Formats in deprecated/ don't need live doc.
Reformatted our largest xmldoc files.
+++ /dev/null
-<para>
- This format reads the binary (.gpb) track logs recorded on
- <ulink url="http://www.dell.com">Dell</ulink> Axim Navigation Systems.
-</para>
-
-<para>
- This is a read-only format for now as the format was reverse
- engineered and there are many unknown bytes. We can successfully
- extract the common GPS data.
-</para>
+++ /dev/null
-
-
-
- <para><ulink url="http://www.cetusgps.dk/">Cetus GPS</ulink> is a program for
-Palm/OS. Working with Ron Parker and Kjeld Jensen, we can now read
-and write files for that program.</para>
-
+++ /dev/null
-
-
-
- <para> This code is mostly intended to convert <ulink url="http://xcski.com/~ptomblin/CoPilot/">CoPilot Flight
-Planner for Palm/OS"</ulink> databases into other formats. You probably should
-not use this to write CoPilot databases, although the code is there,
-because GPSBabel doesn't convert magnetic declination values.</para>
-<para>This version now reads all CoPilot file versions up to 4, but only
-writes version 4 files. If you have a need for a version flag, please let
-me know.</para>
- <para> Questions, bug reports, etc, to ptomblin at
-xcski.com</para>
- <para>
- <ulink url="http://xcski.com/~ptomblin/CoPilot/">http://xcski.com/~ptomblin/CoPilot/</ulink>
-and <ulink url="http://navaid.com/CoPilot/">http://navaid.com/CoPilot</ulink>
- </para>
-
+++ /dev/null
-<para>
-This format supports <productname>cotoGPS</productname>, a <productname>Palm</productname> GPS program.
-It can read both track and marker (waypoint) files. It is currently unable
-to write track files, so only marker files can be written. The marker
-categories are written to and read from the icon description. The 'Not
-Assigned' category leaves the icon description empty on read.
-Currently geocache info is ignored.
-</para>
-<para> In addition to the documented options, this format also has a
-debugging option called <option>internals</option> which takes an XCSV
-delimiter value. It writes some internal values (distance, arc, x and y)
-of the cotoGPS track format to the notes field.
-</para>
-<para>
-Contributed by Tobias Minich.
-</para>
-<para>
-<ulink url="http://core.de/~coto/projects/cotogps/">cotoGPS</ulink>
-</para>
-
+++ /dev/null
-<para>
- The 'delbin' module supports
-<productname>DeLorme PN-20</productname>,
-<productname>DeLorme PN-30</productname>,
-<productname>DeLorme PN-40</productname>,
-<productname>DeLorme PN-40 SE</productname>, and
-<productname>DeLorme PN 60 </productname>receivers.
- <important>
- <para>
- Not all strains of Linux are supported. Fedora 7 is known not to work, for example.
- </para>
- </important>
-</para>
-<para>
- Only the 'usb:' device is supported. If you're on Windows, do not attempt to
- run this through the serial driver.
-</para>
-<para>
- On Linux, a name of the form 'hid:path-to-hidraw,path-to-hiddev' is also supported.
- You will need to use this only if the HID device nodes on your system are not named
- /dev/hidrawN and /dev/hiddevN or /dev/usb/hiddevN.
-</para>
-
-<para>
- This module implements the (undocumented) waypoint extensions introduced
- for enhanced geocaching mode in 2.5 for PN-40 and 1.6 for PN-20. As
- these are reverse engineered, there may be issues with those modes
- in particular.
-</para>
-
-<example id="pn-40-send">
- <title>Command to send a pocket query (GPX) to a DeLorme PN device </title>
- <para>
- <userinput>
- gpsbabel -i gpx -f "My Caches.gpx" -o delbin -F usb:
- </userinput>
- </para>
-</example>
-
-<para>
- If you receive a message that the device is busy, especially on Windows,
- that could be because another program, likely DeLorme's own, has the
- device open even though it's not actively interacting with the GPS. In
- Topo 8, on the GPS tab, look for GPS Options. Uncheck "Start GPS" and
- "Automatically detect GPS". Then just click the Exchange button when
- you're ready for Topo to interact with the GPS. Other DeLorme software may
- be similar.
-</para>
-<para>
- The GPS should not be in 'map exchange' mode. When in that mode, it appears
- as a disk to the USB system, thus GPSBabel will be unable to find the GPS.
-</para>
-<para>
+<para>
GPSBabel supports a wide variety of Garmin hardware via serial
on most operating systems and USB on Windows, Linux, and OS X.
</para>
-<para>
+<para>
For serial models, be sure the GPS is set for "Garmin
mode" in setup and that nothing else (PDA hotsync programs, gpsd,
getty, pppd, etc.) is using the serial port.
</para>
-<para>
- Supported Garmin GPS receivers with USB include
+<para>
+ Supported Garmin GPS receivers with USB include
<simplelist columns="4">
-<member>Astro</member>
-<member>Edge 205</member>
-<member>Edge 305</member>
-<member>eTrex Legend C</member>
-<member>eTrex Legend Cx</member>
-<member>eTrex Legend H</member>
-<member>eTrex Legend HCx</member>
-<member>eTrex Summit Cx</member>
-<member>eTrex Summit HC</member>
-<member>eTrex Venture C</member>
-<member>eTrex Venture Cx</member>
-<member>eTrex Venture HC</member>
-<member>eTrex Vista C</member>
-<member>eTrex Vista Cx</member>
-<member>eTrex Vista H</member>
-<member>eTrex Vista HCx</member>
-<member>Forerunner 205</member>
-<member>Forerunner 301</member>
-<member>Forerunner 305</member>
+<member>Astro</member>
+<member>Edge 205</member>
+<member>Edge 305</member>
+<member>eTrex Legend C</member>
+<member>eTrex Legend Cx</member>
+<member>eTrex Legend H</member>
+<member>eTrex Legend HCx</member>
+<member>eTrex Summit Cx</member>
+<member>eTrex Summit HC</member>
+<member>eTrex Venture C</member>
+<member>eTrex Venture Cx</member>
+<member>eTrex Venture HC</member>
+<member>eTrex Vista C</member>
+<member>eTrex Vista Cx</member>
+<member>eTrex Vista H</member>
+<member>eTrex Vista HCx</member>
+<member>Forerunner 205</member>
+<member>Forerunner 301</member>
+<member>Forerunner 305</member>
<member>Foretrex 201</member>
-<member>Foretrex 301</member>
+<member>Foretrex 301</member>
<member>GPS 18<footnote id="posnonly"><para>This model does not support transfer of waypoints, tracks, or routes, but may be used with the <link linkend="tracking">realtime tracking</link> feature.</para></footnote></member>
-<member>GPSMAP 195</member>
-<member>GPSMAP 276C</member>
-<member>GPSMAP 295</member>
-<member>GPSMAP 296C</member>
-<member>GPSMAP 378</member>
-<member>GPSMAP 396</member>
-<member>GPSMAP 478</member>
+<member>GPSMAP 195</member>
+<member>GPSMAP 276C</member>
+<member>GPSMAP 295</member>
+<member>GPSMAP 296C</member>
+<member>GPSMAP 378</member>
+<member>GPSMAP 396</member>
+<member>GPSMAP 478</member>
<member>GPSMAP 496</member>
-<member>GPSMAP 60C</member>
-<member>GPSMAP 60CS</member>
-<member>GPSMAP 60CSx</member>
-<member>GPSMAP 60Cx</member>
-<member>GPSMAP 76C</member>
-<member>GPSMAP 76CS</member>
-<member>GPSMAP 76CSX</member>
-<member>GPSMAP 76Cx</member>
-<member>GPSMAP 96</member>
-<member>GPSMAP 96C</member>
+<member>GPSMAP 60C</member>
+<member>GPSMAP 60CS</member>
+<member>GPSMAP 60CSx</member>
+<member>GPSMAP 60Cx</member>
+<member>GPSMAP 76C</member>
+<member>GPSMAP 76CS</member>
+<member>GPSMAP 76CSX</member>
+<member>GPSMAP 76Cx</member>
+<member>GPSMAP 96</member>
+<member>GPSMAP 96C</member>
<member>Quest</member>
<member>Quest II</member>
<member>Rhino 520</member>
<member>Rhino 530</member>
<member>Rhino 520 HCx</member>
<member>Rhino 530 HCx</member>
-<member>StreetPilot 2610</member>
-<member>StreetPilot 2620</member>
-<member>StreetPilot 2650</member>
-<member>StreetPilot 2720</member>
-<member>StreetPilot 2730</member>
-<member>StreetPilot 2820</member>
-<member>StreetPilot 7200</member>
-<member>StreetPilot 7500</member>
+<member>StreetPilot 2610</member>
+<member>StreetPilot 2620</member>
+<member>StreetPilot 2650</member>
+<member>StreetPilot 2720</member>
+<member>StreetPilot 2730</member>
+<member>StreetPilot 2820</member>
+<member>StreetPilot 7200</member>
+<member>StreetPilot 7500</member>
<member>StreetPilot c310</member>
<member>StreetPilot c320</member>
<member>StreetPilot c330</member>
<member>eTrex Vista</member>
<member>eTrex (Basic Yellow)</member>
<member>eTrex H</member>
-<member>Forerunner 201</member>
-<member>Foretrex 201</member>
-<member>Geko 201</member>
-<member>Geko 301</member>
-<member>GPS 12CX </member>
-<member>GPS 12Map </member>
-<member>GPS 12 </member>
-<member>GPS 12XL </member>
-<member>GPS III </member>
-<member>GPS III+ </member>
-<member>GPS II </member>
-<member>GPS II+ </member>
-<member>GPS V</member>
-<member>Rhino 110</member>
-<member>Rhino 120</member>
-<member>Rhino 130</member>
-<member>StreetPilot III</member>
-<member>StreetPilot III+</member>
+<member>Forerunner 201</member>
+<member>Foretrex 201</member>
+<member>Geko 201</member>
+<member>Geko 301</member>
+<member>GPS 12CX </member>
+<member>GPS 12Map </member>
+<member>GPS 12 </member>
+<member>GPS 12XL </member>
+<member>GPS III </member>
+<member>GPS III+ </member>
+<member>GPS II </member>
+<member>GPS II+ </member>
+<member>GPS V</member>
+<member>Rhino 110</member>
+<member>Rhino 120</member>
+<member>Rhino 130</member>
+<member>StreetPilot III</member>
+<member>StreetPilot III+</member>
</simplelist>
</para>
<para>
The following Garmin GPS receivers are supported, but they do not
-support Garmin communication protocol and don't work with the
+support Garmin communication protocol and don't work with the
<option>garmin</option> option. To use these receivers, read or write
GPX files from the mass storage device as mounted on your computer.
<simplelist columns="4">
</para>
<para>
- Not every feature on every model is supported. For example,
+ Not every feature on every model is supported. For example,
while we do extract data such as heart rate and temperature from
tracks on the sporting models like Edge and Forerunner, GPSBabel
- is not a fitness program at its core and does not support features
+ is not a fitness program at its core and does not support features
like workouts or calorie/fitness zone data. Furthermore, sporting
models don't support track upload. When trying to upload tracks to
these devices, GPSBabel converts them to courses on the fly and
a speed of 10 km/h for tracks that lack them.
</para>
-<para>
+<para>
To communicate with a Garmin GPS serially, use the name of that
- serial port such as <filename>COM1</filename> or <filename>/dev/cu.serial</filename>.
+ serial port such as <filename>COM1</filename> or <filename>/dev/cu.serial</filename>.
</para>
<para>
- To communicate via USB use <filename>usb:</filename> as the filename on all OSes.
- Thus, to read the waypoints from a Garmin USB receiver and write
+ To communicate via USB use <filename>usb:</filename> as the filename on all OSes.
+ Thus, to read the waypoints from a Garmin USB receiver and write
them to a GPX file:
</para>
<para><userinput>gpsbabel -i garmin -f usb: -o gpx -F blah.gpx</userinput></para>
<para>
- If you have multiple units attached via USB, you may provide
- a unit number, with zero being the implied default. So if you
- have three USB models on your system, they can be addressed as
+ If you have multiple units attached via USB, you may provide
+ a unit number, with zero being the implied default. So if you
+ have three USB models on your system, they can be addressed as
<filename>usb:0</filename>, <filename>usb:1</filename>, and <filename>usb:2</filename>. To get a list of recognized devices,
specify a negative number such as:
</para>
<para><userinput>gpsbabel -i garmin -f usb:-1</userinput></para>
-
-<para>
+
+<para>
When reporting problems with the Garmin format, be sure to include
the full unit model, firmware version, and be prepared to offer
debugging dumps by adding <option>-D9</option> to the command line, like:
<para><userinput> gpsbabel -D9 -i garmin -f usb: -o gpx -F blah.gpx</userinput></para>
-<para>
+<para>
Custom icons are supported on units that support that.
Neither GPSBabel nor your firmware know what is associated with any
given slot number. They don't know that the picture you placed in the
so they are named 'Custom 0' through 'Custom 511'.
</para>
<para>
- For models where the connection on the GPS is a serial interface,
+ For models where the connection on the GPS is a serial interface,
be sure the GPS is set for "Garmin
mode" in setup and that nothing else (PDA hotsync programs, gpsd,
- getty, pppd, etc.) is using the serial port.
+ getty, pppd, etc.) is using the serial port.
</para>
<para>
For models connected via USB, we recommend use of the <filename>usb:</filename>
filename. For this to work on Windows, you must install
the Garmin driver. For Linux, this will fail if you have the garmin_gps
- kernel module loaded.
+ kernel module loaded.
See the <ulink url="/osnotes.html">Operating System Notes</ulink> for details.
</para>
<para>
-This module also supports <link linkend="tracking">realtime tracking</link>
+This module also supports <link linkend="tracking">realtime tracking</link>
which allows realtime position reports from a Garmin GPS receiver over USB
-or serial.
+or serial.
</para>
<important>
-<para>The following Garmin units do not follow the standard Garmin
-communications protocol and are <emphasis>not supported</emphasis>
+<para>The following Garmin units do not follow the standard Garmin
+communications protocol and are <emphasis>not supported</emphasis>
by GPSBabel.</para>
<para>
Marine plotters:
-
-
- <para>This is a very simple format that
+<para>
+ This is a very simple format that
is most useful for exporting data from units that support heart rate
data such as
-<productname>Garmin Forerunner 301</productname>,
-<productname>Garmin Forerunner 305</productname>, and
-<productname>Garmin Edge 305</productname>, and
+
+ <productname>Garmin Forerunner 301</productname>,
+ <productname>Garmin Forerunner 305</productname>, and
+ <productname>Garmin Edge 305</productname>, and
to other programs
for analysis. It's a simple comma delimited format that includes the
timestamp, 3D position information and heart rate so you can pull it
-into a spreadsheet or graphing program. </para>
-
+into a spreadsheet or graphing program.
+</para>
\ No newline at end of file
<para>
-Input format for Garmin G1000 integrated avionics system datalog generated by
-G1000 system software version 563.20 or later. This datalog is automatically
-generated and stored to a standard SD card if one is inserted in the *upper*
-SD card slot on the G1000's MFD (right-hand display on 2-screen installations,
-center display on 3-screen installations).
+Input format for Garmin G1000 integrated avionics system datalog generated by
+G1000 system software version 563.20 or later. This datalog is automatically
+generated and stored to a standard SD card if one is inserted in the *upper*
+SD card slot on the G1000's MFD (right-hand display on 2-screen installations,
+center display on 3-screen installations).
</para>
<para>
-Supports conversion of GPS track (including timestamp) and barometric altitude
-data to any of GPSBabel's output formats. Does not include support for G1000
-stored flight plan (.fpl) route files or user waypoints. Tested on datalogs
-from Cessna 182T and Turbo 182T, but it should accommodate G1000 datalogs
-from other airframes as well. If any conversion failures or errors occur,
-check datalog csv file for incomplete or corrupted records/rows, delete
+Supports conversion of GPS track (including timestamp) and barometric altitude
+data to any of GPSBabel's output formats. Does not include support for G1000
+stored flight plan (.fpl) route files or user waypoints. Tested on datalogs
+from Cessna 182T and Turbo 182T, but it should accommodate G1000 datalogs
+from other airframes as well. If any conversion failures or errors occur,
+check datalog csv file for incomplete or corrupted records/rows, delete
those records/rows from the datalog file and reattempt.
</para>
but it's mangled beyond what we're likely to successfully read.
</para>
<para>
- If a waypoint name is annotated with a trailing '@'NNN where NNN is
+ If a waypoint name is annotated with a trailing '@'NNN where NNN is
a number, that number will be used as the speed for POI alerts, just
as with Garmin's POI Loader program. The units default to metric kilometers
per hour, but this can be changed to statute via the units argument.
</para>
<para>
The layout of GPI files isn't documented and our module was created
- via reverse engineering. If you get a problem on reading or writing
+ via reverse engineering. If you get a problem on reading or writing
a GPI file, please provide that file (mailto:gpsbabel-misc@lists.sourceforge.net).
</para>
<para>
</para>
<para>
This module does not support direct transfer of .GPI files to
- receivers in Garmin protocol mode. For units like Nuvi, Zumo, or
+ receivers in Garmin protocol mode. For units like Nuvi, Zumo, or
Streetpilot, just choose a file that's on the drive where your
- GPS is mounted. For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.)
+ GPS is mounted. For units like the X series (GPSMap 60CSx, GPSMap 60Cx, Legend Hcx, etc.)
you must explicitly put the unit in mass storage mode or mount
- the memory chip in an external reader and transfer the file
+ the memory chip in an external reader and transfer the file
directly.
</para>
</important>
<para>
- The <ulink url="http://www.garmin.com/support/agree.jsp?id=927">Garmin POI loader</ulink>
+ The <ulink url="http://www.garmin.com/support/agree.jsp?id=927">Garmin POI loader</ulink>
loads custom points of interest into certain models of
Garmin GPS receivers. (As of this writing, only the models introduced
in 2005 and later are supported. See Garmin's site for more info.)
This format was mostly useful when POI Loader couldn't read GPX and we
couldn't write GPI. See <link linkend="fmt_garmin_gpi">GPSBabel's GPI doc</link>.
</para>
-
<para>
-This is a textual format that contains nearly all of the information
+This is a textual format that contains nearly all of the information
contained in the <productname>MapSource</productname> main format, <link linkend="fmt_gdb">GDB</link>.
-This format also contains some computed values such as distances between
+This format also contains some computed values such as distances between
routepoints and trackpoints, speed, and course (heading).
</para>
<para>
-The main goal of garmin_txt is to make aviation data more available. Because
-<productname>MapSource</productname> supports only the export, GPSBabel gives you the possibility to
+The main goal of garmin_txt is to make aviation data more available. Because
+<productname>MapSource</productname> supports only the export, GPSBabel gives you the possibility to
bring aviation data into <productname>MapSource</productname>.
</para>
<para>
During the export with <productname>MapSource</productname>, some fields are written using local settings
of <productname>MapSource</productname> and Windows. These include grid format, gps datum, distance and
-temperature units, and the representation of date and time fields. GPSBabel
-tries to read all items automatically. Problems with date and time format can
+temperature units, and the representation of date and time fields. GPSBabel
+tries to read all items automatically. Problems with date and time format can
be solved with the 'date' and 'time' options.
</para>
<example id="all_garmin_txt_options">
<title>Command showing garmin_txt output with all options</title>
<para><userinput>gpsbabel -i garmin_txt,date="MM/DD/YYYY",time="hh:mm:ss xx" -f in.txt -o garmin_txt,date="DD.MM.YYYY",datum="WGS 72",dist=m,prec=6,temp=c,time="HH:mm:ss",utc=+2 -F out.txt</userinput></para>
</example>
-
+
+++ /dev/null
-<para>
- This is format for the
- <ulink url="http://vip.hyperusa.com/~dougs/geocachingdb/geocachingdb.htm"> GeocachingDB</ulink>
- program by DougsBrat. It works with v2 and v3 of this program.
-</para>
-
-<para>
- Input support for the GEOnet Names Server (GNS) country
- file structure. Export to this format is not possible, as this format
- has too many fields that we never get populated by any other
- format.
-</para>
+
+++ /dev/null
-
-
-
- <para><ulink url="http://www.raydarllc.com/">Geoniche</ulink> is a Palm/OS application oriented for the
-off-road user. This module was contributed by Rick Richardson.
- </para>
-
+++ /dev/null
-
-
-
- <para> This format is designed to read the XML emitted when you
-tack "&output=js" onto the end of a <ulink url="http://maps.google.com">Google Maps</ulink> route URL (use
-the "link to this page" option to get a usable URL.) This allows you
-to plan a route using Google Maps, then download it and use it in your
-own mapping program or GPS receiver. To get a file suitable for use
-with GPSBabel, plan your route as usual with Google Maps. Once you've
-got it the way you want it, click the "Link to this page" link in the
-upper right-hand corner of the Google Maps page. Then, edit the URL
-that appears in your address bar by adding "&output=js" (without
-the quotes) onto the end. Hit enter, and the resulting page will be
-mostly empty. It doesn't look like much, but it contains exactly what
-GPSBabel needs. Save it to disk using whatever menu option your web
-browser provides.
-</para>
-<para>
-Note that if you are using Microsoft Internet Explorer, you should make sure
-to save the web page as "Web Page, HTML Only". If you save it as "Web Page,
-Complete", it will be reformatted into a non-XHTML format that GPSBabel
-cannot read.
-</para>
-<para>
-If you use a Unix-compatible
-operating system, this shell script might be useful:
-</para>
-<programlisting format="linespecific">
-#!/bin/sh
-FROM="233 S. Upper Wacker Dr, Chicago, IL"
-TO="1060 W. Addison St, Chicago, IL"
-wget -O - "http://maps.google.com/maps?q=$FROM to $TO&output=js" \
-2&>/dev/null >google_map.js
-gpsbabel -i google -f google_map.js -o gpx -F google_map.gpx
-</programlisting>
-
+++ /dev/null
-
-
-
- <para> This is a Palm/OS file format for
- <ulink url="http://www.cru.fr/perso/cc/GPilotS/">GPilotS</ulink>.
- It was tested against version 6.2 of GPilotS
-</para>
- <para> Neither tracks nor routes are supported at this
-time.</para>
-
+++ /dev/null
-
-
-
- <para>The file format for GPSPILOT <ulink url="http://www.gpspilot.com">gpspilot.com</ulink> was provided by Ron
-Parker. The output from this module has been tested with GPSPilot
-Tracker v5.05sx, but it is based on reverse-engineering so it may not
-work with all versions of all GPSPilot products. It had read-only
-support for Airport, Navaid, City and Landmark files but will read and
-write Point files.</para>
-
<section id="fmt_igc_notes">
<title>IGC Data Format Notes</title>
<para>
-Refer to Appendix 1 of
+Refer to Appendix 1 of
<ulink url="http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp">http://www.fai.org:81/gliding/gnss/tech_spec_gnss.asp</ulink>
for the specification of the IGC data format.
</para>
<para>
A sample list of software applications that use data in IGC format can be
-found at
+found at
<ulink url="http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf">http://www.fai.org:81/gliding/gnss/gnss_analysis_software.pdf</ulink>
</para>
<para>
-<para>
+<para>
Many <ulink url="http://www.lowrance.com">Lowrance</ulink> systems have the ability
to output their data to an external storage device.
Early models (such as iFinder Hunt) supported an MMC card.
When exported the data is saved to the card as a
file. Some models have the ability to export data in GPX format but the
format native to <ulink url="http://www.lowrance.com">Lowrance</ulink> units is called USR.
-Typically the file created by the export operation will have a ".usr" suffix if is a
+Typically the file created by the export operation will have a ".usr" suffix if is a
native format or a ".gpx" suffix if is is a GPX format file.
</para>
Some USR formats also have multiple element versions (i.e. USR version 4 has two different formats for storing
route data).
Depending on the model of device you have you may be able to select the format for export data from any of the
-five USR formats or even the GPX format.
+five USR formats or even the GPX format.
</para>
<para>
(this is based on information contained in the <ulink url="ftp://software.lowrance.com/Documents/Hook2-Series_OM_EN_988-11760-001_w.pdf">2018 Lowrance Hook2 Series Operator Manual</ulink>) and other sources.
</para>
<para>
- <emphasis>User Data File version 2 </emphasis>-
+ <emphasis>User Data File version 2 </emphasis>-
Legacy file format.
This is the default output USR version used by GPSBabel.
It contains only basic information on waypoints, routes, and trails.
</para>
<para>
- <emphasis>User Data File version 3 </emphasis> -
+ <emphasis>User Data File version 3 </emphasis> -
Legacy file format.
Added depth information to Route waypoints.
Supports trails with a maximum of 10,000 trail-points.
Last version that supports Event Marker ICONs.
</para>
<para>
- <emphasis>User Data File version 4</emphasis> -
+ <emphasis>User Data File version 4</emphasis> -
Seems to be the best option for transferring data from older Lowrance units.
Many of the counts (Number of Waypoints, Number of Routes, etc) were exanded from
16-bit integer values (maximum value of 65,535) to 32-bit (maxumum value 2,147,483,647)
</para>
<para>
- <emphasis>User Data File version 5</emphasis> -
+ <emphasis>User Data File version 5</emphasis> -
Lowrance introduced universally unique identifiers (UUIDs) in this version.
</para>
<para>
- <emphasis>User Data File version 6</emphasis> -
- Latest format.
+ <emphasis>User Data File version 6</emphasis> -
+ Latest format.
Supports trail characteristics speed and temperature.
</para>
<entry>-</entry> <entry>-</entry> <entry>-</entry> <entry>X</entry> <entry>X</entry>
<entry> Route Universally Unique ID Number </entry>
<entry> 16 </entry>
- <entry> Appears only in USR 5 and 6 format. Universally Unique Route ID captured
+ <entry> Appears only in USR 5 and 6 format. Universally Unique Route ID captured
as four integers</entry>
</row>
<row valign="middle">
</tbody>
</tgroup>
</table>
-
+
<para>
Some Lowrance units have the ability to export
<ulink url="https://www.topografix.com/gpx.asp">GPX</ulink> (GPS Exchange Format) formatted data.
Lowrance only provides minimal
-support for GPX export data on their HOOK2 series (only data available to the author). Refer to
+support for GPX export data on their HOOK2 series (only data available to the author). Refer to
the official <ulink url="https://www.topografix.com/gpx/1/1/">GPX 1.1 Schema Documentation</ulink> for the complete schema.
</para>
<example>
+++ /dev/null
-
-
-
- <para> With this format we support the Palm/OS export for
-Map&Guide based products like "PowerRoute",
-"Motorrad-Routenplaner" and (maybe) other software. The exported files
-can contain maps and/or route descriptions. The reader for this format
-has been tested with PowerRoute 5+6, Motorrad-Routenplaner
-2002(-2006).</para>
-
+++ /dev/null
-<para>
-<ulink url="http://www.magellangs.com">Magellan</ulink> NAV Companion for Palm/OS is not really designed
-for this sort of use, but its file format is supported and with a
-little bit of patience you can both read and write NAV Companion
-waypoints. This conversion is based on
-partially incomplete reverse-engineering of the record format, so it
-may not work with all versions of NAV Companion. It has been tested
-with version 2.10 and 3.20.
-</para>
-<para>
-Translating NAV Companion waypoints to another format is as easy
-as with any other format. Just find the Companion_Waypoints database
-in your palm backup directory and use it as the input file.
-</para>
-<para>
-When translating waypoints back to NAV Companion, though, you need
-to jump through some hoops:
-</para>
-<para>
-First, you must merge any waypoints that already exist in the database
-in your Palm Backup directory with the ones you are adding; failure to
-do so will result in only the new points being available in NAV Companion,
-even if you give the new database a different name (it will overwrite
-the old database, even in your backup directory. That's a feature of
-PalmOS, not of NAV Companion.)
-</para>
-<para>
-To merge the databases, use a command line like the following:
-</para>
-<para><userinput>gpsbabel -i magnav -f Companion_Waypoints.PDB -i geo -f geocaching.loc -o magnav -F merged.pdb</userinput></para>
-<para>
-Second, you must use the installer to install your new PDB file. Don't
-make the mistake of copying it over the existing Companion_Waypoints.PDB
-file; the one on the handheld will overwrite it rather than merging with
-it.
-</para>
-<para>
-Finally, because NAV Companion is not designed to work with desktop
-applications, you must tell NAV Companion that its waypoints database
-has changed out from under it. One way to do this is to go to the
-waypoints screen and attempt to scroll; that will force it to reread
-the database and fix the record pointers that it keeps on the heap.
-</para>
-
+++ /dev/null
-<para>
- Input support for Microsoft AutoRoute 2002-2006 .axe files
- and Microsoft Streets and Trips .est files. This is for reading routes
- created this program and is different than the <link linkend="fmt_s_and_t">
- s_and_t</link> format used for writing pushpins.</para><para>
- These files contains only routes. We can extract the coordinates and
- the names of the points within route. An export to this format will
- not be supported.
-</para>
-
-<para>
- Only the start, stops, and end points are stored in the
- .est/.axe/.ptm files. Turn-by-turn route data is not stored in the
- .est/.axe/.ptm files, and is recalculated by the Microsoft title each
- time on opening the file. This means that the output of GPSBabel will
- not contain turns needed for driving directions.
-</para>
-<para>
- One possible approach to achieve similar results is to
- use the Streets and Trips drawing tools to trace a line over the
- interesting parts of the route to capture intersections or key turns.
- GPSBabel will capture stops in the route and insert those as turns, so
- adding stops at intersections can also improve the results when converting.
-</para>
-
+++ /dev/null
-
-
-
- <para> Input support for Microsoft AutoRoute 2002-2006 .axe files
-and Microsoft Streets and Trips .est files. This is for reading routes
-created this program and is different than the <link linkend="fmt_s_and_t">
-s_and_t</link> format used for writing pushpins.</para><para>
-These files contains only routes. We can extract the coordinates and
-the names of the points within route. An export to this format will
-not be supported.</para>
- <para>Only the start, stops, and end points are stored in the
-.est/.axe/.ptm files. Turn-by-turn route data is not stored in the
-.est/.axe/.ptm files, and is recalculated by the Microsoft title each
-time on opening the file. This means that the output of GPSBabel will
-not contain turns needed for driving directions.</para>
- <para>One possible approach to achieve similar results is to
-use the Streets and Trips drawing tools to trace a line over the
-interesting parts of the route to capture intersections or key turns.
-GPSBabel will capture stops in the route and insert those as turns, so
-adding stops at intersections can also improve the results when converting.
-</para>
-
<para>
- This format is used to exchange data with the <ulink url="http://www.openstreetmap.org">OpenStreetMap</ulink> project.
+ This format is used to exchange data with the <ulink url="http://www.openstreetmap.org">OpenStreetMap</ulink> project.
The main goal of this collaborative project is to create free editable maps.
</para>
<para>
negative numbers will be used as identifier. This has been tested with <ulink url="http://wiki.openstreetmap.org/index.php/JOSM">JOSM</ulink>.
</para>
<para>
- Because the resulting timestamps of OSM ways differ from real GPS tracks,
+ Because the resulting timestamps of OSM ways differ from real GPS tracks,
we read OSM ways into routes. On the output side we write all available routes and tracks into the osm target file.
</para>
-<para>
- OziExplorer Waypoint Format - Another CSV format file.
+<para>OziExplorer Waypoint Format - Another CSV format file.
Tested against OziExplorer v 3.90.3a / Shareware. Contributed by Alex Mottram
-</para>
-
+</para>
\ No newline at end of file
+++ /dev/null
-<para>
- PalmDoc output is similar to <link linkend="fmt_text">Text</link>
- output, except that it generates a Palm Database (PDB) file suitable for
- use with programs like CSpotRun, TealDoc, AportisDoc, Palm Reader, and
- others. The resulting file also contains bookmarks to make it easy to jump
- to a particular waypoint.
-</para>
-<para>
- The following command line reads a GPX file with Groundspeak extensions
- and writes a Palm document with encrypted hints and logs:
-</para>
-<para><userinput>gpsbabel -i gpx -f 12345.gpx -o "palmdoc,dbname=Unfound Geocaches,encrypt,logs" -F 12345.pdb</userinput>
-</para>
-
+++ /dev/null
-<para>
- PathAway is a Palm software designed for handling "most"
- GPS devices (including BlueTooth). In this time (I mean 2005) a free
- tool to convert this database is located on the homepage of PathAway
- (www.pathaway.com). But I've read there ... for windows and the output
- formats are also very limited.
-</para>
-
+++ /dev/null
-<para>
-Microsoft's PocketStreets 2002 Pushpin (.PSP) format is
-not yet completely documented. <emphasis>The .PSP module does not work with
-MS Streets & Trips 2002 .EST files</emphasis> To create .PSP files from
-Streets & Trips 2002, you will need to have PocketStreets support
-installed.
-</para>
-<para>
-Please note that MS Streets & Trips only <emphasis>exports</emphasis>
-.PSP files. It does not import them. MS Streets & Trips 2002 only
-imports CSV files. To use .PSP files, simply copy them over to the
-same folder on the mobile device as the map (.MPS), and open
-PocketStreets. It should also be noted that in the case a pushpin is
-outside of the exported map area, the pin will be "grayed-out" and
-unused in PocketStreets. This is a good thing as it allows us to
-create one big .PSP file that covers multiple .MPS files.
-Unfortunately, you need one .PSP file for every .MPS file.
-</para>
-<section id="fmt_psp_faq">
-<title>Frequently Asked Questions</title>
-<qandaset id="fmt_psp_faq_questions">
-<qandaentry id="why">
-<question>
-<para>
-Why should I use GPSBabel/psp to make pushpins when Streets & Trips (S&T)
- already does that for me?
-</para>
-</question>
-<answer>
-<para>
-GPSBabel/psp has the advantage of being able to create pushpins
-<emphasis>without</emphasis>
- creating the associated map file and the need to "import" the waypoint
- data into S&T. Through a series of scripts, you can create a dozen
- or so PSP files in a few seconds as opposed to a few weeks using the
- S&T interface. The maps are not going to change between sessions,
- only the pins will. Why waste all that time creating maps when all you
- really want are updated pins? As an aside, GPSBabel/psp creates points
- <emphasis>with the proper coordinates</emphasis>
- where S&T does not in some areas of the U.S.
- (Nashville, TN for instance).
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="blank">
-<question>
-<para>
-I keep getting a blank (32 byte) PSP file.
-</para>
-</question>
-<answer>
-<para>
-There are either no points to write, or you have botched the command
- line for GPSBabel. GPSBabel is sensitive to UPPER and lower case
- on the command line. A simple command line to create PSP files
- looks like this:
-</para>
-<para><userinput>gpsbabel -i geo -f geocaching.loc -o psp -F NewOrleans.psp</userinput></para>
-<para>
- Note the use of "-f" for INPUT files and "-F" for OUTPUT files.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="now_what">
-<question>
-<para>
-I've created a PSP file, now what do I do with it?
-</para>
-</question>
-<answer>
-<para>
-To use pushpins in Pocketstreets, you need to have both a map and a
- pushpin file. These two files must exist in the same folder and have
- exactly the same base name as the map. For example, the pins that
- correspond to the map "NewOrleans.mps" should be named "NewOrleans.psp".
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="no_map">
-<question>
-<para>
-I don't have a map. What do I do now?
-</para>
-</question>
-<answer>
-<para>
-Create one using the "Export map to Pocketstreets" option in S&T. You
- can also pick up some major city maps on the web from the MS Pocketstreets
- website if you are interested in seeing how it works.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="have_est">
-<question>
-<para>
-I have .EST files, not .PSP files. What's up with that?
-</para>
-</question>
-<answer>
-<para>
-In order to make PSP files, you need to use the "Export map to
- Pocketstreets" function in S&T. .EST files are for use in S&T, not
- Pocketstreets.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="coord_jitter">
-<question>
-<para>
- The .PSP files differ when I use GPSBabel/psp versus Pocketstreets to
- create them. What's up?
-</para>
-</question>
-<answer>
-<para>
-Pocketstreets makes corrections to the S&T waypoint data upon initial
- loading. GPSBabel/psp writes PSP files with these corrections already made.
- Ask MS.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="mappoint">
-<question>
-<para>
-Does GPSBabel/psp work with (Autoroute, Mappoint, etc..) .PSP files?
-</para>
-</question>
-<answer>
-<para>
-As of this writing, I haven't seen any so I can't be sure. If they
- follow the same layout as S&T 2002, I'd imagine so.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="after2001">
-<question>
-<para>
- Does GPSBabel/psp work with (S&T 2001, S&T 2002, etc...) files?
-</para>
-</question>
-<answer>
-<para>
-MS changed the file layout between S&T 2001 and S&T 2002. The GPSBabel psp
- module is known to work fine with S&T 2002 and 2003.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="non_us">
-<question>
-<para>
-Does GPSBabel/psp work with (insert your country/location here) maps?
-</para>
-</question>
-<answer>
-<para>
-If it doesn't, feel free to inquire on the
-<ulink url="https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc">GPSBabel-Misc</ulink>
-mailing list.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="wrong_coords">
-<question>
-<para>
-What do you mean S&T writes points with the wrong coordinates?
-</para>
-</question>
-<answer>
-<para>
-At some point in the "Export map to Pocketstreets" function in S&T,
- it goofs the lat/long data. Points in Nashville tended to shift
- 1.4 miles WEST of their original location. I'm not a geometry buff,
- but I'd imagine they have a reference point for generating coordinates
- that's wrong in (at least) that area.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="splitting">
-<question>
-<para>
-I have 800 waypoints that cover a dozen or so Pocketstreets maps.
- Do I need to to split my points up into smaller chunks to match the
- area covered by the maps?
-</para>
-</question>
-<answer>
-<para>
- No. Pocketstreets will "ignore" points that are outside of the map
- area. Points that are not on the current map will be "grayed out"
- in pushpin explorer in Pocketsreets. This is the reason the PSP
- module was written for GPSBabel in the first place.
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="doc_for_layout">
-<question>
-<para>
-Where can I find documentation for the layout of PSP files?
-</para>
-</question>
-<answer>
-<para>
-Just about everything I know about the PSP file format is documented
- in the source. To the best of my knowledge, there is no documentation
- (and for good reason, I've come to discover).
-</para>
-</answer>
-</qandaentry>
-<qandaentry id="morehelp">
-<question>
-<para>
-I have some other problem, what do I do?
-</para>
-</question>
-<answer>
-<para>
-Ask your question on the <ulink url="https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc">GPSBabel-Misc</ulink> mailing list.
-</para>
-</answer>
-</qandaentry>
-</qandaset>
-</section>
-
+++ /dev/null
-
-
-
- <para> QuoVadis for Palm OS <ulink url="http://www.marcosoft.com/">marcosoft.com</ulink> is a program for
-Palm/OS. Working with record definitions provided by MarcoSoft and
-further experimentation by Bruce Thompson and "Fuzzy" from the
-Geocaching Forums to nail down the format precisely.</para>
- <para> Should work fine for import and export.</para>
- <para> One thing of note, QuoVadis stores all waypoints in a
-single Palm Database without using categories. This means that it may
-be difficult to keep personal waypoints separate from generated
-waypoints. What Bruce recommends is taking the QuoVadisMarkerDB.PDB
-file synced down from your Palm Powered device and extract the
-waypoints you personally set to a GPX file. Then using GPSBabel's
-joining capabilities generate a new PDB file from the personal file
-and the other waypoint files of interest.</para>
- <para> Currently the selection of icons to display and the scale
-at which to display them is hardcoded. Also there is no support for
-notes associated with waypoints. This will be addressed in a future
-revision.</para>
-
<para>
Unicsv examines the first line of a file to determine the field
- order and field separator in that file. On write, it tries to
+ order and field separator in that file. On write, it tries to
figure out what data it has and writes headers and all the data it can.
</para>
<para>
diff = <link linkend="style_def_geodiff">Geocache difficulty</link>
ele = Elevation (in meters) of the point. Add "ft" or "feet" for feet.
e/w = 'e' for eastern hemisphere, 'w' for western
- exported = Geocache export date
+ exported = Geocache export date
found = <link linkend="style_def_geofound">Geocache last found date</link>
fix = 3d, 2d, etc.
gcid = Geocache cache id
y_pos = Latitude
z = Altitude (elevation). See "elevation".
</screen>
- We support some enhanced Garmin attributes. They are also available in
- <link linkend="fmt_gpx">gpx</link>, <link linkend="fmt_gdb">gdb</link>,
- <link linkend="fmt_garmin_gpi">garmin_gpi</link> and partly
- <link linkend="fmt_garmin_txt">garmin_txt</link>. These entities are currently
- not visible in <productname>MapSource</productname> (6.12.4), but are NOT dropped
+ We support some enhanced Garmin attributes. They are also available in
+ <link linkend="fmt_gpx">gpx</link>, <link linkend="fmt_gdb">gdb</link>,
+ <link linkend="fmt_garmin_gpi">garmin_gpi</link> and partly
+ <link linkend="fmt_garmin_txt">garmin_txt</link>. These entities are currently
+ not visible in <productname>MapSource</productname> (6.12.4), but are NOT dropped
when working with GDB (version 3) or GPX files.
<screen></screen>
Please note, that these do NOT provide a geocoding service; don't expect
<para>
A typical file may be:
<screen format="linespecific">
- Name, Latitude, Longitude, Description
+ Name, Latitude, Longitude, Description
GCEBB,35.972033,-87.134700,Mountain Bike Heaven by susy1313
GC1A37,36.090683,-86.679550,The Troll by a182pilot & Family
</screen>
projects / gpsbabel.git / commitdiff